Skip to content

chore: Configure Renovate#128

Closed
renovate[bot] wants to merge 5 commits into
mainfrom
renovate/configure
Closed

chore: Configure Renovate#128
renovate[bot] wants to merge 5 commits into
mainfrom
renovate/configure

Conversation

@renovate

@renovate renovate Bot commented Oct 14, 2025

Copy link
Copy Markdown

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.


Detected Package Files

  • .docker/compose.yml (docker-compose)
  • .devcontainer/Dockerfile (dockerfile)
  • .docker/Dockerfile (dockerfile)
  • .github/workflows/auto-release.yaml (github-actions)
  • .github/workflows/codeql.yml (github-actions)
  • .github/workflows/ghcr-build-nightly.yaml (github-actions)
  • .github/workflows/ghcr-build-release.yaml (github-actions)
  • .github/workflows/test-build.yml (github-actions)
  • go.mod (gomod)
  • frontend/package.json (npm)

Configuration Summary

Based on the default config's presets, Renovate will:

  • Start dependency updates only once this onboarding PR is merged
  • Hopefully safe environment variables to allow users to configure.
  • Show all Merge Confidence badges for pull requests.
  • Enable Renovate Dependency Dashboard creation.
  • Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
  • Ignore node_modules, bower_components, vendor and various test/tests (except for nuget) directories.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • Show only the Age and Confidence Merge Confidence badges for pull requests.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.
  • Use semantic prefixes for commit messages and PR titles.
  • Rebase existing PRs any time the base branch has been updated.
  • Limit to maximum 10 open PRs at any time.
  • Rate limit PR creation to a maximum of four per hour.
  • Apply labels renovate and {{arg1}} to PRs.
  • Remove hourly and concurrent rate limits.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.


You have configured Renovate to use the following baseBranchPatterns: v7-nightly, nightly.

What to Expect

With your current configuration, Renovate will create 14 Pull Requests:

chore(deps): update dependency go to v1.25.2 (v7-nightly)
  • Schedule: ["at any time"]
  • Branch name: renovate/v7-nightly-github-actions
  • Merge into: v7-nightly
  • Upgrade go to 1.25.2
chore(deps): update dependency svelte to v5.39.11 (v7-nightly)
  • Schedule: ["at any time"]
  • Branch name: renovate/v7-nightly-svelte-5.x-lockfile
  • Merge into: v7-nightly
  • Upgrade svelte to 5.39.11
fix(deps): update go modules (minor/patch) (v7-nightly)
chore(deps): update dependency @​sveltejs/vite-plugin-svelte to v6 (v7-nightly)
  • Schedule: ["at any time"]
  • Branch name: renovate/v7-nightly-sveltejs-vite-plugin-svelte-6.x
  • Merge into: v7-nightly
  • Upgrade @sveltejs/vite-plugin-svelte to ^6.0.0
chore(deps): update dependency vite to v7 (v7-nightly)
  • Schedule: ["at any time"]
  • Branch name: renovate/v7-nightly-vite-7.x
  • Merge into: v7-nightly
  • Upgrade vite to ^7.0.0
chore(deps): update dependency wait-on to v9 (v7-nightly)
  • Schedule: ["at any time"]
  • Branch name: renovate/v7-nightly-wait-on-9.x
  • Merge into: v7-nightly
  • Upgrade wait-on to ^9.0.0
chore(deps): update github-actions (v7-nightly) (major)
chore(deps): update dependency go to v1.25.2 (nightly)
  • Schedule: ["at any time"]
  • Branch name: renovate/nightly-github-actions
  • Merge into: nightly
  • Upgrade go to 1.25.2
chore(deps): update dependency svelte to v5.39.11 (nightly)
  • Schedule: ["at any time"]
  • Branch name: renovate/nightly-svelte-5.x-lockfile
  • Merge into: nightly
  • Upgrade svelte to 5.39.11
fix(deps): update go modules (minor/patch) (nightly)
chore(deps): update dependency @​sveltejs/vite-plugin-svelte to v6 (nightly)
  • Schedule: ["at any time"]
  • Branch name: renovate/nightly-sveltejs-vite-plugin-svelte-6.x
  • Merge into: nightly
  • Upgrade @sveltejs/vite-plugin-svelte to ^6.0.0
chore(deps): update dependency vite to v7 (nightly)
  • Schedule: ["at any time"]
  • Branch name: renovate/nightly-vite-7.x
  • Merge into: nightly
  • Upgrade vite to ^7.0.0
chore(deps): update dependency wait-on to v9 (nightly)
  • Schedule: ["at any time"]
  • Branch name: renovate/nightly-wait-on-9.x
  • Merge into: nightly
  • Upgrade wait-on to ^9.0.0
chore(deps): update github-actions (nightly) (major)

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.


This PR was generated by Mend Renovate. View the repository job log.

@JacksonTheMaster

Copy link
Copy Markdown
Member

@mitoskalandiel Looks good to me (now), what do you think?

@mitoskalandiel

Copy link
Copy Markdown
Contributor

Can't say until it's run

@JacksonTheMaster

JacksonTheMaster commented Oct 14, 2025

Copy link
Copy Markdown
Member

Can't say until it's run

Of course you can, just read the PR

What to Expect

_With your current configuration, Renovate will create 13 Pull Requests _

@mitoskalandiel

Copy link
Copy Markdown
Contributor

yeah, i guess its fine

@mitoskalandiel mitoskalandiel deleted the renovate/configure branch October 17, 2025 11:56
@renovate

renovate Bot commented Oct 17, 2025

Copy link
Copy Markdown
Author

Renovate is disabled

Renovate is disabled because there is no Renovate configuration file. To enable Renovate, you can either (a) change this PR's title to get a new onboarding PR, and merge the new onboarding PR, or (b) create a Renovate config file, and commit that file to your base branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants